-
Notifications
You must be signed in to change notification settings - Fork 531
Gracefully handle common errors in credential values #1026
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 looks good!
Codecov Report
@@ Coverage Diff @@
## master #1026 +/- ##
============================================
+ Coverage 66.14% 66.18% +0.03%
+ Complexity 3468 3466 -2
============================================
Files 739 739
Lines 17443 17425 -18
Branches 963 961 -2
============================================
- Hits 11537 11532 -5
+ Misses 5366 5357 -9
+ Partials 540 536 -4
Continue to review full report at Codecov.
|
@mediumTaj could you take another look real quick? I just had to add some null checks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 looks good!
The functional change in this PR is that exceptions are thrown for credential values surrounded by
{}
or""
characters. This prevents making a call to the service and provides a more helpful error message.Besides that, there was a lot of refactoring done with the credential logic in the SDK. Things had gotten a bit messy with the various changes we've had in auth methods and one-off fixes, so I consolidated some things to make it a bit clearer to work with. This should also make it easier to add the next auth feature coming soon 👀